fix insight blueprints navigation #6633
Merged
+24
−24
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
github-actions
bot
added
the
Playground
Contributor
Author
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #6633 +/- ##
=======================================
Coverage 54.98% 54.98%
=======================================
Files 888 888
Lines 55753 55753
Branches 3816 3816
=======================================
Hits 30653 30653
Misses 25005 25005
Partials 95 95
🚀 New features to boost your workflow:
|
![graphite-app[bot]](https://avatars.githubusercontent.com/in/158384?s=60&v=4){kind=small}
MananTank
reviewed
Apr 3, 2025
Contributor
size-limit report 📦
|
iuwqyir
force-pushed
the
04-03-fix_insight_blueprints_navigation
branch
from
daf068d to
444db07
Compare
iuwqyir
force-pushed
the
04-03-fix_insight_blueprints_navigation
branch
from
444db07 to
be59923
Compare
MananTank
approved these changes
Apr 3, 2025
Contributor
Merge activity
|
## [Dashboard] Feature: Update API path format and add token lookup endpoint
## Notes for the reviewer
This PR updates the API path format in `insightBlueprints.ts` to use curly braces for path parameters (e.g., changing `/v1/transactions/:contractAddress` to `/v1/transactions/{contractAddress}`). This standardizes our path format to match OpenAPI specifications.
## How to test
The changes can be verified by checking the updated paths in the playground interface to ensure they display correctly with the new format.
<!-- start pr-codex -->
---
## PR-Codex overview
This PR focuses on updating the URL path parameters in the `insightBlueprints` to use curly braces `{}` instead of colons `:` for better clarity and consistency in API endpoints.
### Detailed summary
- Changed path parameters from `:paramName` to `{paramName}` for various endpoints:
- `/v1/transactions/:contractAddress` to `/v1/transactions/{contractAddress}`
- `/v1/wallets/:wallet_address/transactions` to `/v1/wallets/{wallet_address}/transactions`
- Updated multiple other endpoints similarly, including:
- `/v1/events/:contractAddress` to `/v1/events/{contractAddress}`
- `/v1/tokens/transfers/:contract_address` to `/v1/tokens/transfers/{contract_address}`
- `/v1/nfts/:contract_address` to `/v1/nfts/{contract_address}`
- And many more throughout the file.
> ✨ Ask PR-Codex anything about this PR by commenting with `/codex {your question}`
<!-- end pr-codex -->
graphite-app
bot
force-pushed
the
04-03-fix_insight_blueprints_navigation
branch
from
be59923 to
cf02af0
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[Dashboard] Feature: Update API path format and add token lookup endpoint
Notes for the reviewer
This PR updates the API path format in
insightBlueprints.tsto use curly braces for path parameters (e.g., changing/v1/transactions/:contractAddressto/v1/transactions/{contractAddress}). This standardizes our path format to match OpenAPI specifications.How to test
The changes can be verified by checking the updated paths in the playground interface to ensure they display correctly with the new format.
PR-Codex overview
This PR focuses on updating the API path parameters in the
insightBlueprintsto use curly braces{}instead of colons:. This change aims to standardize the path parameter syntax across the API specifications.Detailed summary
:to{}for various API endpoints, including:Get contract transactionsGet wallet transactionsGet contract eventsGet token transfersGet ERC-20, ERC-721, ERC-1155 balancesResolveGet contract ABI and metadataGet NFT owners and transfersForce refresh collection and token metadata